Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6daa8ba8815aa87a0d3bd3fe5b0480402c3ab859e106532b2da6a3d31f360a

Tx prefix hash: 63c3020f8b735fc970d701da825f83a94d2e2c714dde0bb8c2b5266164bfb1e0
Tx public key: 6cd49f3cdc5004d12ba9440da9b204730e42a5cb5bdca766a2f2941433c69cae
Timestamp: 1681035880 Timestamp [UCT]: 2023-04-09 10:24:40 Age [y:d:h:m:s]: 02:018:07:25:49
Block: 734783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535245 RingCT/type: yes/0
Extra: 016cd49f3cdc5004d12ba9440da9b204730e42a5cb5bdca766a2f2941433c69cae021100000001b3164c24000000000000000000

1 output(s) for total of 2.256164041000 dcy

stealth address amount amount idx
00: bca2b4f230fb6088425217344f3b5adfbf76d5653103c69f1f716713ac37549a 2.256164041000 1181034 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": 734793, "vin": [ { "gen": { "height": 734783 } } ], "vout": [ { "amount": 2256164041, "target": { "key": "bca2b4f230fb6088425217344f3b5adfbf76d5653103c69f1f716713ac37549a" } } ], "extra": [ 1, 108, 212, 159, 60, 220, 80, 4, 209, 43, 169, 68, 13, 169, 178, 4, 115, 14, 66, 165, 203, 91, 220, 167, 102, 162, 242, 148, 20, 51, 198, 156, 174, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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