Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d4fa3b4de76684b361617cf107d9f058aae067ede529021da85793e8aac40c7

Tx prefix hash: 0b4b822f6ba6ab8efadc5d4855df9307e3cfa9365ea4df1361d61a59b6310148
Tx public key: 6e722b70253b3fd8a05ce859ef4995083c1efa45f769d9b4b9ec99de6bca401c
Timestamp: 1764660929 Timestamp [UCT]: 2025-12-02 07:35:29 Age [y:d:h:m:s]: 00:005:10:11:51
Block: 1424685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3882 RingCT/type: yes/0
Extra: 016e722b70253b3fd8a05ce859ef4995083c1efa45f769d9b4b9ec99de6bca401c02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f02f141830695f8ee161cd0f01bc69b7c5c37fdfff52d727d472bca15969a38 0.600000000000 1913316 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": 1424695, "vin": [ { "gen": { "height": 1424685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f02f141830695f8ee161cd0f01bc69b7c5c37fdfff52d727d472bca15969a38" } } ], "extra": [ 1, 110, 114, 43, 112, 37, 59, 63, 216, 160, 92, 232, 89, 239, 73, 149, 8, 60, 30, 250, 69, 247, 105, 217, 180, 185, 236, 153, 222, 107, 202, 64, 28, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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