Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ffcc4dc2a24d7139035151e11bf05f7f73e4f4267db09051c5472d7c282f687

Tx prefix hash: 967ce8fd44f2016c4eb909c2c70c055f7d4b80ca3a47a451fff66aeecf958c5e
Tx public key: 0e833f4d1ad60c067d1e0e48f6dee4ae7ed4a63b237debc6c1bbf219e579e41b
Timestamp: 1718284329 Timestamp [UCT]: 2024-06-13 13:12:09 Age [y:d:h:m:s]: 00:133:19:12:54
Block: 1043332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95798 RingCT/type: yes/0
Extra: 010e833f4d1ad60c067d1e0e48f6dee4ae7ed4a63b237debc6c1bbf219e579e41b0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3445ec950821020b909fd819927f2dc3e54c41c05a646cc88e5177c6da936bc6 0.600000000000 1512461 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": 1043342, "vin": [ { "gen": { "height": 1043332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3445ec950821020b909fd819927f2dc3e54c41c05a646cc88e5177c6da936bc6" } } ], "extra": [ 1, 14, 131, 63, 77, 26, 214, 12, 6, 125, 30, 14, 72, 246, 222, 228, 174, 126, 212, 166, 59, 35, 125, 235, 198, 193, 187, 242, 25, 229, 121, 228, 27, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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