Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbf8dbc8f52ae1086018672af48f7629274ba86ea4a56d84cb6d3e2dc8b8eee

Tx prefix hash: 69f4f2771390be3628cf06db894ffeb694cbdb150b3274fee449b827812fe053
Tx public key: 6dcdc67d0ecf58dc60d6bb51abd2e3269e47ee3b40e59633282cc18d4df37445
Timestamp: 1725457592 Timestamp [UCT]: 2024-09-04 13:46:32 Age [y:d:h:m:s]: 00:127:23:15:07
Block: 1102811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91517 RingCT/type: yes/0
Extra: 016dcdc67d0ecf58dc60d6bb51abd2e3269e47ee3b40e59633282cc18d4df3744502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ee9fcf01699a8f44e7dd565dd4e37a6c42cc2cbe9255f3a3a503f17437f543 0.600000000000 1579390 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": 1102821, "vin": [ { "gen": { "height": 1102811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ee9fcf01699a8f44e7dd565dd4e37a6c42cc2cbe9255f3a3a503f17437f543" } } ], "extra": [ 1, 109, 205, 198, 125, 14, 207, 88, 220, 96, 214, 187, 81, 171, 210, 227, 38, 158, 71, 238, 59, 64, 229, 150, 51, 40, 44, 193, 141, 77, 243, 116, 69, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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