Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f878358b9a4fc15d4ef853fb598784cfeaaef62e3f4a9265dc39fa7c5a29375d

Tx prefix hash: e2903921b657646a4568b8d73a8845e55cc831c7956b9669c44f4c23b24ad804
Tx public key: ba7ce5d24d1ffe337ec2f8caae2878b764172e5d3d8d434e7216b728be761492
Timestamp: 1621528431 Timestamp [UCT]: 2021-05-20 16:33:51 Age [y:d:h:m:s]: 03:194:06:06:20
Block: 264134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 900435 RingCT/type: yes/0
Extra: 01ba7ce5d24d1ffe337ec2f8caae2878b764172e5d3d8d434e7216b728be761492021100000104fdc4fdba000000000000000000

1 output(s) for total of 81.811612584000 dcy

stealth address amount amount idx
00: fb67cffd255bf4eba2f6a7fd44653a41a13101571f20b9f2ad14b3cc4c92b168 81.811612584000 555468 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": 264144, "vin": [ { "gen": { "height": 264134 } } ], "vout": [ { "amount": 81811612584, "target": { "key": "fb67cffd255bf4eba2f6a7fd44653a41a13101571f20b9f2ad14b3cc4c92b168" } } ], "extra": [ 1, 186, 124, 229, 210, 77, 31, 254, 51, 126, 194, 248, 202, 174, 40, 120, 183, 100, 23, 46, 93, 61, 141, 67, 78, 114, 22, 183, 40, 190, 118, 20, 146, 2, 17, 0, 0, 1, 4, 253, 196, 253, 186, 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