Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5e90f802365f92181c472deeede5d4478460f489042444c9a9dd3b5c983874

Tx prefix hash: a786b9d7ddb94b0f801e31a040e5b8ee591395c570f424d37950452fd0140908
Tx public key: ad2f801760b08f945334a6949fdc633d02650ba58c534911fca76df3be19f796
Timestamp: 1728383046 Timestamp [UCT]: 2024-10-08 10:24:06 Age [y:d:h:m:s]: 00:156:12:12:37
Block: 1127054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111654 RingCT/type: yes/0
Extra: 01ad2f801760b08f945334a6949fdc633d02650ba58c534911fca76df3be19f796021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16249e68a60912234e51e6d727ee13cf5a64c853cf4a6671f37dc8dab2a52d5a 0.600000000000 1609853 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": 1127064, "vin": [ { "gen": { "height": 1127054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16249e68a60912234e51e6d727ee13cf5a64c853cf4a6671f37dc8dab2a52d5a" } } ], "extra": [ 1, 173, 47, 128, 23, 96, 176, 143, 148, 83, 52, 166, 148, 159, 220, 99, 61, 2, 101, 11, 165, 140, 83, 73, 17, 252, 167, 109, 243, 190, 25, 247, 150, 2, 17, 0, 0, 0, 5, 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