Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dcbebbd841b7f34af0688c07e0d36b4b05254ddea7b839321ecafe8092437a8

Tx prefix hash: 313c14de28abddc792bab2a8d2a1fa152cdc5c9ae876753f8b550157d4cd97be
Tx public key: 39b858ea3e9adab396e5f540c4297f53feee8588ff2b0522af094ffa6bb03c80
Timestamp: 1732780665 Timestamp [UCT]: 2024-11-28 07:57:45 Age [y:d:h:m:s]: 00:125:19:35:46
Block: 1163414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89716 RingCT/type: yes/0
Extra: 0139b858ea3e9adab396e5f540c4297f53feee8588ff2b0522af094ffa6bb03c800211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a61630885362a40c6c9ac9869d34d55c0d091949136ca6d3bd0f7f46d24cb4a8 0.600000000000 1649081 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": 1163424, "vin": [ { "gen": { "height": 1163414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a61630885362a40c6c9ac9869d34d55c0d091949136ca6d3bd0f7f46d24cb4a8" } } ], "extra": [ 1, 57, 184, 88, 234, 62, 154, 218, 179, 150, 229, 245, 64, 196, 41, 127, 83, 254, 238, 133, 136, 255, 43, 5, 34, 175, 9, 79, 250, 107, 176, 60, 128, 2, 17, 0, 0, 0, 3, 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