Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0afbda3618251a125faac9831f484d0a30d9778110c03302c2a30ab613e99c

Tx prefix hash: 5570c9e5c0ac37602bf73dd4f7a0449ddb779985b8d6d31813fe285bf951ede1
Tx public key: 9e501b08d041ee5169313053799e34790aebe36ce1cbb0a4915057fcfc1f4a84
Timestamp: 1693230150 Timestamp [UCT]: 2023-08-28 13:42:30 Age [y:d:h:m:s]: 01:147:20:06:20
Block: 835789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366984 RingCT/type: yes/0
Extra: 019e501b08d041ee5169313053799e34790aebe36ce1cbb0a4915057fcfc1f4a8402110000000375e3f0e9000000000000000000

1 output(s) for total of 1.043960743000 dcy

stealth address amount amount idx
00: d7d6ea160f1d8983b062fd2ff6fbd6d06625be64053411c01493b4a53f9412bc 1.043960743000 1288357 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": 835799, "vin": [ { "gen": { "height": 835789 } } ], "vout": [ { "amount": 1043960743, "target": { "key": "d7d6ea160f1d8983b062fd2ff6fbd6d06625be64053411c01493b4a53f9412bc" } } ], "extra": [ 1, 158, 80, 27, 8, 208, 65, 238, 81, 105, 49, 48, 83, 121, 158, 52, 121, 10, 235, 227, 108, 225, 203, 176, 164, 145, 80, 87, 252, 252, 31, 74, 132, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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