Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bc8a6f9b71ef4d47b6bd35d698e22ae6f22f198245d3f3869ca7a71bacce19b

Tx prefix hash: 2b31bbd0a9f8028cf4bc5986fbff5c6b7eedb80498389dacef44cea15b46f483
Tx public key: 517ef10a5a29160c03bd39f456c2e71dca96578f8d93356fa05fa74f39fcc6e5
Timestamp: 1722096047 Timestamp [UCT]: 2024-07-27 16:00:47 Age [y:d:h:m:s]: 01:102:16:07:38
Block: 1074934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331870 RingCT/type: yes/0
Extra: 01517ef10a5a29160c03bd39f456c2e71dca96578f8d93356fa05fa74f39fcc6e502110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e09ea4d4507f6ae5cecf32b737c5dc41a5074aa65ef3cb8ba32fb228241925a8 0.600000000000 1547453 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": 1074944, "vin": [ { "gen": { "height": 1074934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e09ea4d4507f6ae5cecf32b737c5dc41a5074aa65ef3cb8ba32fb228241925a8" } } ], "extra": [ 1, 81, 126, 241, 10, 90, 41, 22, 12, 3, 189, 57, 244, 86, 194, 231, 29, 202, 150, 87, 143, 141, 147, 53, 111, 160, 95, 167, 79, 57, 252, 198, 229, 2, 17, 0, 0, 0, 12, 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