Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ce787cae73af6a09b87de9ff024fd79c9c48741ad88c28e46b5e10302b51b8

Tx prefix hash: 26d9c33e309f8d4a9ef76ee539be2e81a0b0cd48a9365dec2025be6fcf8bba51
Tx public key: 136a1764c84d2574b3a8dafee6235936e9e41da2eae0de9da29e6beb800fa90d
Timestamp: 1672975883 Timestamp [UCT]: 2023-01-06 03:31:23 Age [y:d:h:m:s]: 02:121:21:53:19
Block: 668568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608832 RingCT/type: yes/0
Extra: 01136a1764c84d2574b3a8dafee6235936e9e41da2eae0de9da29e6beb800fa90d02110000000371bd5189000000000000000000

1 output(s) for total of 3.739010111000 dcy

stealth address amount amount idx
00: 7f1c03ae67db83192e6ef6c23a6c5022c2ba108d9a423f92af5551198ed74dae 3.739010111000 1109819 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": 668578, "vin": [ { "gen": { "height": 668568 } } ], "vout": [ { "amount": 3739010111, "target": { "key": "7f1c03ae67db83192e6ef6c23a6c5022c2ba108d9a423f92af5551198ed74dae" } } ], "extra": [ 1, 19, 106, 23, 100, 200, 77, 37, 116, 179, 168, 218, 254, 230, 35, 89, 54, 233, 228, 29, 162, 234, 224, 222, 157, 162, 158, 107, 235, 128, 15, 169, 13, 2, 17, 0, 0, 0, 3, 113, 189, 81, 137, 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