Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464e4cd27d82165ebcab951a6371943f8398a583608b7e3a384659c944575a41

Tx prefix hash: 5a5d1c14d4a14639a8a58e9f8433218b7e3c3274a297dc2a8d7f6938e8a77d17
Tx public key: bed810632f4d7e43108de84d6037182c40da790532358d3b8a8cb21156c0b6c5
Timestamp: 1728658419 Timestamp [UCT]: 2024-10-11 14:53:39 Age [y:d:h:m:s]: 00:043:16:48:54
Block: 1129335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31211 RingCT/type: yes/0
Extra: 01bed810632f4d7e43108de84d6037182c40da790532358d3b8a8cb21156c0b6c5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f86a8701857ccadea3942b2e1dc54d8d4d0c16d5958498c870be91916879c53a 0.600000000000 1612160 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": 1129345, "vin": [ { "gen": { "height": 1129335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f86a8701857ccadea3942b2e1dc54d8d4d0c16d5958498c870be91916879c53a" } } ], "extra": [ 1, 190, 216, 16, 99, 47, 77, 126, 67, 16, 141, 232, 77, 96, 55, 24, 44, 64, 218, 121, 5, 50, 53, 141, 59, 138, 140, 178, 17, 86, 192, 182, 197, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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