Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb7f4bd3b2eedfcd564c6ccf116c3af0f20bbf60d23de13ee2ae8ebab14b902f

Tx prefix hash: cd9a8cf6148b7d12777189206dfe996f0c47401d2ddc04e2834f73e3dd985ac8
Tx public key: 62bb5560fdde1a29f6418c99deaec67d9c7b53dad4cf173b2c70d1a1ff7bed94
Timestamp: 1701095996 Timestamp [UCT]: 2023-11-27 14:39:56 Age [y:d:h:m:s]: 01:108:10:20:00
Block: 900835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338665 RingCT/type: yes/0
Extra: 0162bb5560fdde1a29f6418c99deaec67d9c7b53dad4cf173b2c70d1a1ff7bed9402110000000be6d27f9c000000000000000000

1 output(s) for total of 0.635564561000 dcy

stealth address amount amount idx
00: fc09ad50d74ebdfe66c9fca6a224c539d24f02fdad15a458bb629ba1319b6849 0.635564561000 1357358 of 0

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": 900845, "vin": [ { "gen": { "height": 900835 } } ], "vout": [ { "amount": 635564561, "target": { "key": "fc09ad50d74ebdfe66c9fca6a224c539d24f02fdad15a458bb629ba1319b6849" } } ], "extra": [ 1, 98, 187, 85, 96, 253, 222, 26, 41, 246, 65, 140, 153, 222, 174, 198, 125, 156, 123, 83, 218, 212, 207, 23, 59, 44, 112, 209, 161, 255, 123, 237, 148, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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