Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a81d710eb405384dc118ef39b57138ed04feae202a0641a224d1eb5f0e049c

Tx prefix hash: 663f879def7476919fe186b0e786067dceac6b21dd34fb36d40cc6e350499f1d
Tx public key: bee15c07589dfbe7d49ced591775dcb83e377ea44901e97b2d9e4e82ad3945d0
Timestamp: 1711998817 Timestamp [UCT]: 2024-04-01 19:13:37 Age [y:d:h:m:s]: 00:364:14:28:30
Block: 991190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260693 RingCT/type: yes/0
Extra: 01bee15c07589dfbe7d49ced591775dcb83e377ea44901e97b2d9e4e82ad3945d00211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbfa406fcd6e598a34d0f1bbe6e7380827ca6f8e5039c653de22b9dcf70fbfec 0.600000000000 1451524 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": 991200, "vin": [ { "gen": { "height": 991190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbfa406fcd6e598a34d0f1bbe6e7380827ca6f8e5039c653de22b9dcf70fbfec" } } ], "extra": [ 1, 190, 225, 92, 7, 88, 157, 251, 231, 212, 156, 237, 89, 23, 117, 220, 184, 62, 55, 126, 164, 73, 1, 233, 123, 45, 158, 78, 130, 173, 57, 69, 208, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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