Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3132ce7567a00f6f2b08a1a120b65dfb6eacf9c2603140860c34d038ec6ed2

Tx prefix hash: 7cd62f19c12bfdd23310c83a6bd9b66b267a166074c058d582099fccf22bf251
Tx public key: 1714de75d8927e6831897b775e52f39f5a2c4c287761944c655a29a7aa8bbe80
Timestamp: 1734481350 Timestamp [UCT]: 2024-12-18 00:22:30 Age [y:d:h:m:s]: 00:118:06:30:48
Block: 1177529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84295 RingCT/type: yes/0
Extra: 011714de75d8927e6831897b775e52f39f5a2c4c287761944c655a29a7aa8bbe800211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c7e2d1d82cacab39f538f96f19f819e923da50552cf3d7904fa1c4aa2ca092 0.600000000000 1663900 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": 1177539, "vin": [ { "gen": { "height": 1177529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c7e2d1d82cacab39f538f96f19f819e923da50552cf3d7904fa1c4aa2ca092" } } ], "extra": [ 1, 23, 20, 222, 117, 216, 146, 126, 104, 49, 137, 123, 119, 94, 82, 243, 159, 90, 44, 76, 40, 119, 97, 148, 76, 101, 90, 41, 167, 170, 139, 190, 128, 2, 17, 0, 0, 0, 1, 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