Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334ad454f62652c125fe67480a84072ae14d7beb50072f7253ad7f9f63d1f43a

Tx prefix hash: bc6c89251bea603620b5aa6fd21f36ba8ad55e62ccb86e7bfe85e2083bf95cfc
Tx public key: ec3f58c48153885d59ff8da2687213db7d3bbc13073370edb3b1a2f2d9661b93
Timestamp: 1703858413 Timestamp [UCT]: 2023-12-29 14:00:13 Age [y:d:h:m:s]: 01:110:10:52:15
Block: 923734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340045 RingCT/type: yes/0
Extra: 01ec3f58c48153885d59ff8da2687213db7d3bbc13073370edb3b1a2f2d9661b9302110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8c5085b60e8bc514693e048361f058943132611a2b0a0d239ab8580fc75e2f 0.600000000000 1381470 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": 923744, "vin": [ { "gen": { "height": 923734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8c5085b60e8bc514693e048361f058943132611a2b0a0d239ab8580fc75e2f" } } ], "extra": [ 1, 236, 63, 88, 196, 129, 83, 136, 93, 89, 255, 141, 162, 104, 114, 19, 219, 125, 59, 188, 19, 7, 51, 112, 237, 179, 177, 162, 242, 217, 102, 27, 147, 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