Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8670a48f8236529117449e23f535b825b4a20dabddc25b3452009dfca36d9d25

Tx prefix hash: 1d98ab8f226fbc92e7fe3aa7d726b09ec37862e8bfc237415d9e0cbcdd08234a
Tx public key: c41885b42f280a3db58bf7041562bd77d5153a1bb5c5268139efa581a8c942d3
Timestamp: 1726379060 Timestamp [UCT]: 2024-09-15 05:44:20 Age [y:d:h:m:s]: 00:117:02:10:18
Block: 1110437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83729 RingCT/type: yes/0
Extra: 01c41885b42f280a3db58bf7041562bd77d5153a1bb5c5268139efa581a8c942d302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92a31dbd4a5110466d0948c38b59b55d97b10b5a9f5a6c7d834ef1a05721744a 0.600000000000 1589042 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": 1110447, "vin": [ { "gen": { "height": 1110437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92a31dbd4a5110466d0948c38b59b55d97b10b5a9f5a6c7d834ef1a05721744a" } } ], "extra": [ 1, 196, 24, 133, 180, 47, 40, 10, 61, 181, 139, 247, 4, 21, 98, 189, 119, 213, 21, 58, 27, 181, 197, 38, 129, 57, 239, 165, 129, 168, 201, 66, 211, 2, 17, 0, 0, 0, 1, 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