Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511e03864a379a76d965a760d77b71e07e49b7cb77f7a303521307483bdd2301

Tx prefix hash: 2f03fd554cfdd0b864653b73c5619fdf7f520f39895ce908c15132be468cd13a
Tx public key: 9fddfbc1995a2f082d8ef0e01f43917568c0e2c8f09b4ca3e7ac8cebb29b7281
Timestamp: 1733911358 Timestamp [UCT]: 2024-12-11 10:02:38 Age [y:d:h:m:s]: 00:096:01:11:58
Block: 1172791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68445 RingCT/type: yes/0
Extra: 019fddfbc1995a2f082d8ef0e01f43917568c0e2c8f09b4ca3e7ac8cebb29b7281021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58de61b81e4e792e29f2d807f0c18b68e920ec8ef6aacd67dd0baf9422702a0b 0.600000000000 1658726 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": 1172801, "vin": [ { "gen": { "height": 1172791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58de61b81e4e792e29f2d807f0c18b68e920ec8ef6aacd67dd0baf9422702a0b" } } ], "extra": [ 1, 159, 221, 251, 193, 153, 90, 47, 8, 45, 142, 240, 224, 31, 67, 145, 117, 104, 192, 226, 200, 240, 155, 76, 163, 231, 172, 140, 235, 178, 155, 114, 129, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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