Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848fba60793e4c823db9cb042b9e023c9d3d752f5c4c9ec0d1244bfcdd95ce1a

Tx prefix hash: 4dc378b6d2203d309e242b874a8d59616c9d87e1b9ac2a59bb7d9317b381ab40
Tx public key: 1d45fd18fe4f1559af7f50f924d6c4cc0cc284f9930db578ef283a940948fbb5
Timestamp: 1721256125 Timestamp [UCT]: 2024-07-17 22:42:05 Age [y:d:h:m:s]: 00:245:10:27:50
Block: 1067979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175344 RingCT/type: yes/0
Extra: 011d45fd18fe4f1559af7f50f924d6c4cc0cc284f9930db578ef283a940948fbb502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 147715d1e9b1c140feb1f40411ce5f524dcdeb333343684de91c8cfa3c63313a 0.600000000000 1538944 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": 1067989, "vin": [ { "gen": { "height": 1067979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "147715d1e9b1c140feb1f40411ce5f524dcdeb333343684de91c8cfa3c63313a" } } ], "extra": [ 1, 29, 69, 253, 24, 254, 79, 21, 89, 175, 127, 80, 249, 36, 214, 196, 204, 12, 194, 132, 249, 147, 13, 181, 120, 239, 40, 58, 148, 9, 72, 251, 181, 2, 17, 0, 0, 0, 2, 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