Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b622ea15ddb9615c27af3f29b5f9569058bf2f40f70f211605f05703eb7023c9

Tx prefix hash: 8ee1d2ab75f3f900239fa9e70c12bb5fd698c8bd5d63e70d14160dccca2b35a6
Tx public key: d92ffd2d76bea241d144110cdd56d98afdbdc1cdce148578633b5970a2eec0da
Timestamp: 1736770721 Timestamp [UCT]: 2025-01-13 12:18:41 Age [y:d:h:m:s]: 00:064:23:18:50
Block: 1196447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46227 RingCT/type: yes/0
Extra: 01d92ffd2d76bea241d144110cdd56d98afdbdc1cdce148578633b5970a2eec0da021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8fac458be96ab38833f8aaf4dfa0c7a5ad48a85cf5c5fcee2c62e4e307458c6 0.600000000000 1683046 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": 1196457, "vin": [ { "gen": { "height": 1196447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8fac458be96ab38833f8aaf4dfa0c7a5ad48a85cf5c5fcee2c62e4e307458c6" } } ], "extra": [ 1, 217, 47, 253, 45, 118, 190, 162, 65, 209, 68, 17, 12, 221, 86, 217, 138, 253, 189, 193, 205, 206, 20, 133, 120, 99, 59, 89, 112, 162, 238, 192, 218, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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