Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd48e28d529d6d86bc712ed667013ee6a50c13b25a2a611ec786465c819f30cb

Tx prefix hash: e8090726d716f8c6eec47e319bb96eedc09bc9d5f1dd8e496c2636e277bd24ae
Tx public key: eaae068cf040d4c4de120f96bc4129332c476dee0aee80826207766ac989cdd7
Timestamp: 1701344097 Timestamp [UCT]: 2023-11-30 11:34:57 Age [y:d:h:m:s]: 01:176:21:34:29
Block: 902864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387655 RingCT/type: yes/0
Extra: 01eaae068cf040d4c4de120f96bc4129332c476dee0aee80826207766ac989cdd7021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.625801717000 dcy

stealth address amount amount idx
00: fe8cbd654af9db2a85fa1658be8128430977fd6ea6957826741220ae7da2b6b8 0.625801717000 1359527 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": 902874, "vin": [ { "gen": { "height": 902864 } } ], "vout": [ { "amount": 625801717, "target": { "key": "fe8cbd654af9db2a85fa1658be8128430977fd6ea6957826741220ae7da2b6b8" } } ], "extra": [ 1, 234, 174, 6, 140, 240, 64, 212, 196, 222, 18, 15, 150, 188, 65, 41, 51, 44, 71, 109, 238, 10, 238, 128, 130, 98, 7, 118, 106, 201, 137, 205, 215, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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