Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f272b0233ec46a432917f84aad49fca4c7e63efda7d28aa400cfee887d89f65

Tx prefix hash: 2813ee314b8518689972512553b945bfbf5cc81663efda3dc95b2c9d4e5165f3
Tx public key: ec0ae60a262a1af6d8de8289b6f6d0899e8ddf582cbdd0e8443dc54a3bf8148d
Timestamp: 1765888890 Timestamp [UCT]: 2025-12-16 12:41:30 Age [y:d:h:m:s]: 00:025:04:15:15
Block: 1434856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18045 RingCT/type: yes/0
Extra: 01ec0ae60a262a1af6d8de8289b6f6d0899e8ddf582cbdd0e8443dc54a3bf8148d02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f47196394070bf61c3801abf114654ccf293ab0a2cc39655a802fbc48e97fef5 0.600000000000 1923653 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": 1434866, "vin": [ { "gen": { "height": 1434856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f47196394070bf61c3801abf114654ccf293ab0a2cc39655a802fbc48e97fef5" } } ], "extra": [ 1, 236, 10, 230, 10, 38, 42, 26, 246, 216, 222, 130, 137, 182, 246, 208, 137, 158, 141, 223, 88, 44, 189, 208, 232, 68, 61, 197, 74, 59, 248, 20, 141, 2, 17, 0, 0, 0, 3, 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