Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31c0e000365c67ebb142a6a029583248c73b0c8850cbf9a783e2b98a3e1b0823

Tx prefix hash: 9dca7fc8fa282c155807c22bb92d378df6f50346ac4ebd8e2452434d8f15bf07
Tx public key: 611af4058c0fb504d37ae9e1353eff802a14c750c6d682b20188ec0cb1426447
Timestamp: 1674474027 Timestamp [UCT]: 2023-01-23 11:40:27 Age [y:d:h:m:s]: 02:315:10:14:19
Block: 681002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744828 RingCT/type: yes/0
Extra: 01611af4058c0fb504d37ae9e1353eff802a14c750c6d682b20188ec0cb142644702110000000183600029000000000000000000

1 output(s) for total of 3.400616187000 dcy

stealth address amount amount idx
00: 894005041959f56c35a0d53d2d43f57c34c9f5d3c80c3a68bbce5df30e6643a7 3.400616187000 1123079 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": 681012, "vin": [ { "gen": { "height": 681002 } } ], "vout": [ { "amount": 3400616187, "target": { "key": "894005041959f56c35a0d53d2d43f57c34c9f5d3c80c3a68bbce5df30e6643a7" } } ], "extra": [ 1, 97, 26, 244, 5, 140, 15, 181, 4, 211, 122, 233, 225, 53, 62, 255, 128, 42, 20, 199, 80, 198, 214, 130, 178, 1, 136, 236, 12, 177, 66, 100, 71, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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