Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6cf505111de87aafb4597b4ead37a1549bd6437337bf6bf5e8095376f419e1

Tx prefix hash: 69bbd7af86e84e52429af79bd0e8d0c5adbb70dc72407f7681a32b1e8c7bf224
Tx public key: 3120bb8d0dc2bbe6ae55fcaedb718bc510e51af1281fe2368c5f6d8992764390
Timestamp: 1735245356 Timestamp [UCT]: 2024-12-26 20:35:56 Age [y:d:h:m:s]: 00:113:00:19:46
Block: 1183821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80575 RingCT/type: yes/0
Extra: 013120bb8d0dc2bbe6ae55fcaedb718bc510e51af1281fe2368c5f6d89927643900211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b831e1a2ef655c65dec18065ba43f120d99cc55da839bb0294c12d8521e4e4b7 0.600000000000 1670270 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": 1183831, "vin": [ { "gen": { "height": 1183821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b831e1a2ef655c65dec18065ba43f120d99cc55da839bb0294c12d8521e4e4b7" } } ], "extra": [ 1, 49, 32, 187, 141, 13, 194, 187, 230, 174, 85, 252, 174, 219, 113, 139, 197, 16, 229, 26, 241, 40, 31, 226, 54, 140, 95, 109, 137, 146, 118, 67, 144, 2, 17, 0, 0, 0, 2, 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