Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 15fce9095fb66684b4c793db93fda575e19ade0cf45896ecb265bb697d40c72e

Tx prefix hash: 4a1754e1564f138d6a8f59ca56ad2933d82c7850a0e1654f8a08029f5dd329ef
Tx public key: 2bdb39c2490e70313361fc7b198fce723023275e7b273bbd25e847c27440b0fe
Timestamp: 1709971047 Timestamp [UCT]: 2024-03-09 07:57:27 Age [y:d:h:m:s]: 01:055:07:12:38
Block: 974424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300520 RingCT/type: yes/0
Extra: 012bdb39c2490e70313361fc7b198fce723023275e7b273bbd25e847c27440b0fe02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 478d44113fb6ed1bdb7931753d9a2b727aff64c741d19ea07c4eb81f916e8b5e 0.600000000000 1434379 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 974434, "vin": [ { "gen": { "height": 974424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "478d44113fb6ed1bdb7931753d9a2b727aff64c741d19ea07c4eb81f916e8b5e" } } ], "extra": [ 1, 43, 219, 57, 194, 73, 14, 112, 49, 51, 97, 252, 123, 25, 143, 206, 114, 48, 35, 39, 94, 123, 39, 59, 189, 37, 232, 71, 194, 116, 64, 176, 254, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8