Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f673c26001122fbd89e5b39e081d4aa560068c8a5dd2d6ad8fea9fc159f634f3

Tx prefix hash: 75e284644f833e14e323cbae2dbe3e2b1ef5e588450658f2a506517ad8054af3
Tx public key: 5432025e9ddf28c839022239e4a0241ecce5a875ddc74a964a8d13f8da2d465a
Timestamp: 1706360729 Timestamp [UCT]: 2024-01-27 13:05:29 Age [y:d:h:m:s]: 00:346:03:17:28
Block: 944456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247824 RingCT/type: yes/0
Extra: 015432025e9ddf28c839022239e4a0241ecce5a875ddc74a964a8d13f8da2d465a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c55f33217c066ff8b647b9da522120b4e798a3b8a1ed4d1dfe6bd4702ddfdbb 0.600000000000 1402700 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": 944466, "vin": [ { "gen": { "height": 944456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c55f33217c066ff8b647b9da522120b4e798a3b8a1ed4d1dfe6bd4702ddfdbb" } } ], "extra": [ 1, 84, 50, 2, 94, 157, 223, 40, 200, 57, 2, 34, 57, 228, 160, 36, 30, 204, 229, 168, 117, 221, 199, 74, 150, 74, 141, 19, 248, 218, 45, 70, 90, 2, 17, 0, 0, 0, 4, 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