Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91a65f361eb6f465565f59b0a62943e15222c9169aad963563b83573d06cb90f

Tx prefix hash: 7c32614a6abe5575ea272fc4e0bd581fcacbe737520cf5c9ad77f63e0e92035a
Tx public key: a61f82419513eda32120bb916d0e95f6653c6ff752501ad38fdc72c8e5586a2d
Timestamp: 1721647897 Timestamp [UCT]: 2024-07-22 11:31:37 Age [y:d:h:m:s]: 00:295:14:54:04
Block: 1071210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211228 RingCT/type: yes/0
Extra: 01a61f82419513eda32120bb916d0e95f6653c6ff752501ad38fdc72c8e5586a2d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb06a89f3b48a44e7998f4f5ccc32a0fa82847a677cf2c14f8e5b1e243e0ace5 0.600000000000 1543347 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": 1071220, "vin": [ { "gen": { "height": 1071210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb06a89f3b48a44e7998f4f5ccc32a0fa82847a677cf2c14f8e5b1e243e0ace5" } } ], "extra": [ 1, 166, 31, 130, 65, 149, 19, 237, 163, 33, 32, 187, 145, 109, 14, 149, 246, 101, 60, 111, 247, 82, 80, 26, 211, 143, 220, 114, 200, 229, 88, 106, 45, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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