Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4871142ee22504b8436055643680bd65fc033dfd6ddaecf97f86500491451607

Tx prefix hash: 5fe4d4338096d62054c35b83b99ac00254ca6db6f65aee2144b46db20031fa89
Tx public key: f042f0b779254533b94e3c3fe5d18f8fd2d9bfcb94e5da5ad39bdf746cbce5f8
Timestamp: 1737376378 Timestamp [UCT]: 2025-01-20 12:32:58 Age [y:d:h:m:s]: 00:149:00:05:07
Block: 1201418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106241 RingCT/type: yes/0
Extra: 01f042f0b779254533b94e3c3fe5d18f8fd2d9bfcb94e5da5ad39bdf746cbce5f80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600100000000 dcy

stealth address amount amount idx
00: bf0c1780b420168fb682d40dab221fc50d618d08818360f51c4775cd5f153bdc 0.600100000000 1688069 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": 1201428, "vin": [ { "gen": { "height": 1201418 } } ], "vout": [ { "amount": 600100000, "target": { "key": "bf0c1780b420168fb682d40dab221fc50d618d08818360f51c4775cd5f153bdc" } } ], "extra": [ 1, 240, 66, 240, 183, 121, 37, 69, 51, 185, 78, 60, 63, 229, 209, 143, 143, 210, 217, 191, 203, 148, 229, 218, 90, 211, 155, 223, 116, 108, 188, 229, 248, 2, 17, 0, 0, 0, 4, 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