Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415bb8f429c39cf2458168786d5b2d2f0ec39fb9500b064c32b322454782a575

Tx prefix hash: 208e8df77e62078ed908f3ac629e02e354cfcea165ded52889df428406b048e2
Tx public key: 3e2c64a03c32be68d76af878f2534db1f2837bdb4e04328b4cfecdd2a6b3ffff
Timestamp: 1731516757 Timestamp [UCT]: 2024-11-13 16:52:37 Age [y:d:h:m:s]: 00:141:23:24:22
Block: 1152942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101296 RingCT/type: yes/0
Extra: 013e2c64a03c32be68d76af878f2534db1f2837bdb4e04328b4cfecdd2a6b3ffff021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 074605da16c6bb584e3320b14ecc5d19a3b8dab9c24c6b3db551bea7693b78fd 0.600000000000 1638549 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": 1152952, "vin": [ { "gen": { "height": 1152942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "074605da16c6bb584e3320b14ecc5d19a3b8dab9c24c6b3db551bea7693b78fd" } } ], "extra": [ 1, 62, 44, 100, 160, 60, 50, 190, 104, 215, 106, 248, 120, 242, 83, 77, 177, 242, 131, 123, 219, 78, 4, 50, 139, 76, 254, 205, 210, 166, 179, 255, 255, 2, 17, 0, 0, 0, 3, 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