Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7165684292ffc1d0eb124ea51a16972f753b97786740a60633155eee3c1e0013

Tx prefix hash: d0bb086741c421deaf62415b02913e918d7e81923d09e6f4270bd0c3ad8342e5
Tx public key: eddc78c2ecd6a12ac94f268cd55f1958ca7ac0cbb8f64b7720d4b1fbb5b87a63
Timestamp: 1734896658 Timestamp [UCT]: 2024-12-22 19:44:18 Age [y:d:h:m:s]: 00:081:23:33:25
Block: 1180966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58361 RingCT/type: yes/0
Extra: 01eddc78c2ecd6a12ac94f268cd55f1958ca7ac0cbb8f64b7720d4b1fbb5b87a6302110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd1e793deb975b29152a3df27b043a18e97836a3dde66997dd24aa27eb93132c 0.600000000000 1667381 of 15

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": 1180976, "vin": [ { "gen": { "height": 1180966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd1e793deb975b29152a3df27b043a18e97836a3dde66997dd24aa27eb93132c" } } ], "extra": [ 1, 237, 220, 120, 194, 236, 214, 161, 42, 201, 79, 38, 140, 213, 95, 25, 88, 202, 122, 192, 203, 184, 246, 75, 119, 32, 212, 177, 251, 181, 184, 122, 99, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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