Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989784b0019a86f91f6e409b0c3ea94d708f2219d347ced6ba262dbbc0b9a4e2

Tx prefix hash: 9a43d724da1c05e252e85198f2ce9ccb2ffad9994df926413dc2d9414e870f31
Tx public key: 4a4f3b76c9876732b7d502274634bdb4761f3ece3dbb23e796e346240f32aeac
Timestamp: 1648457216 Timestamp [UCT]: 2022-03-28 08:46:56 Age [y:d:h:m:s]: 02:354:00:54:45
Block: 468101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772370 RingCT/type: yes/0
Extra: 014a4f3b76c9876732b7d502274634bdb4761f3ece3dbb23e796e346240f32aeac021100000007a8c141c5000000000000000000

1 output(s) for total of 17.257875089000 dcy

stealth address amount amount idx
00: 7f0702204ce3712c0fa27a10c111c7d27cfcbe5f05bfe27b19a78dc03a1b13c7 17.257875089000 886747 of 0

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": 468111, "vin": [ { "gen": { "height": 468101 } } ], "vout": [ { "amount": 17257875089, "target": { "key": "7f0702204ce3712c0fa27a10c111c7d27cfcbe5f05bfe27b19a78dc03a1b13c7" } } ], "extra": [ 1, 74, 79, 59, 118, 201, 135, 103, 50, 183, 213, 2, 39, 70, 52, 189, 180, 118, 31, 62, 206, 61, 187, 35, 231, 150, 227, 70, 36, 15, 50, 174, 172, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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