Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff2cf9693809fb4f938f068f128102c6d02d22c78a0ca1e907d7397138522c2

Tx prefix hash: 9a73e5e5ce7797635d209002b4ae862cd31d2934db3c52a1f7727bb81954ce9a
Tx public key: e26ecf7a7317c35e577b7fb434f02298ad0666eb28bde024d748a07e0c8ba406
Timestamp: 1732895868 Timestamp [UCT]: 2024-11-29 15:57:48 Age [y:d:h:m:s]: 00:115:02:57:52
Block: 1164371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82074 RingCT/type: yes/0
Extra: 01e26ecf7a7317c35e577b7fb434f02298ad0666eb28bde024d748a07e0c8ba4060211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3259084dad47f5dfaf95f2387126e833b0983a22f03d0efa2ff5f2f27f4cc7d0 0.600000000000 1650044 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": 1164381, "vin": [ { "gen": { "height": 1164371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3259084dad47f5dfaf95f2387126e833b0983a22f03d0efa2ff5f2f27f4cc7d0" } } ], "extra": [ 1, 226, 110, 207, 122, 115, 23, 195, 94, 87, 123, 127, 180, 52, 240, 34, 152, 173, 6, 102, 235, 40, 189, 224, 36, 215, 72, 160, 126, 12, 139, 164, 6, 2, 17, 0, 0, 0, 5, 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