Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc3ecaa1f2e3bce8b79b2a4014250b4424688d4c03b146011bd0f505578d64d

Tx prefix hash: 7d53d77ae3ca5353065dd513832e54d3fca7248ae61b25606b61933f31630985
Tx public key: 646274626928f8d4d9696d9c22a30d2810dbe12905f889afe24feb0b28dd74d6
Timestamp: 1672036836 Timestamp [UCT]: 2022-12-26 06:40:36 Age [y:d:h:m:s]: 02:316:05:07:30
Block: 660800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745377 RingCT/type: yes/0
Extra: 01646274626928f8d4d9696d9c22a30d2810dbe12905f889afe24feb0b28dd74d6021100000009e7ace25d000000000000000000

1 output(s) for total of 3.967301985000 dcy

stealth address amount amount idx
00: 1a83a7e85fb17f68feb862ca821db3a2d80a92a38fb6142587d13d696f15c036 3.967301985000 1101539 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": 660810, "vin": [ { "gen": { "height": 660800 } } ], "vout": [ { "amount": 3967301985, "target": { "key": "1a83a7e85fb17f68feb862ca821db3a2d80a92a38fb6142587d13d696f15c036" } } ], "extra": [ 1, 100, 98, 116, 98, 105, 40, 248, 212, 217, 105, 109, 156, 34, 163, 13, 40, 16, 219, 225, 41, 5, 248, 137, 175, 226, 79, 235, 11, 40, 221, 116, 214, 2, 17, 0, 0, 0, 9, 231, 172, 226, 93, 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