Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a91306f79c8a2c9abe4e9ef77df2295e1469ac1428766c22423c97d5f7e5a99

Tx prefix hash: 38aa8f4c7963c17e11d74a9c279a88df186fe89d84c495d0ec421c19b39bbdb5
Tx public key: 359b2593c9ba17dde7c82515d02f26826d2ba98211c4efb47ac4339da68b08ed
Timestamp: 1737551402 Timestamp [UCT]: 2025-01-22 13:10:02 Age [y:d:h:m:s]: 00:146:13:00:51
Block: 1202877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104473 RingCT/type: yes/0
Extra: 01359b2593c9ba17dde7c82515d02f26826d2ba98211c4efb47ac4339da68b08ed021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4871fbde6ce1c1d9d83121e450a20646b249a1de6eda9fa1e2ef33459641af28 0.600000000000 1689544 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": 1202887, "vin": [ { "gen": { "height": 1202877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4871fbde6ce1c1d9d83121e450a20646b249a1de6eda9fa1e2ef33459641af28" } } ], "extra": [ 1, 53, 155, 37, 147, 201, 186, 23, 221, 231, 200, 37, 21, 208, 47, 38, 130, 109, 43, 169, 130, 17, 196, 239, 180, 122, 196, 51, 157, 166, 139, 8, 237, 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