Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35882257d83cc8493039a3ad5f7486d7a153cee0dfb24be58a169221e1a9b9a7

Tx prefix hash: 5f1b51439af889831d36fffb523e8a866e8e04b6bc2ea1b9c330e9981b057518
Tx public key: bf4e893a295bbe310506f2ddbc9ea4178815b86bd18974727a3121b87517da91
Timestamp: 1744771326 Timestamp [UCT]: 2025-04-16 02:42:06 Age [y:d:h:m:s]: 00:216:20:34:40
Block: 1262417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152710 RingCT/type: yes/0
Extra: 01bf4e893a295bbe310506f2ddbc9ea4178815b86bd18974727a3121b87517da910211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10fd9af4047f1af396d17ae2588acd6fa68c7faf2c49a9143f572913f92a941e 0.600000000000 1749596 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": 1262427, "vin": [ { "gen": { "height": 1262417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10fd9af4047f1af396d17ae2588acd6fa68c7faf2c49a9143f572913f92a941e" } } ], "extra": [ 1, 191, 78, 137, 58, 41, 91, 190, 49, 5, 6, 242, 221, 188, 158, 164, 23, 136, 21, 184, 107, 209, 137, 116, 114, 122, 49, 33, 184, 117, 23, 218, 145, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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