Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f30a6499c8f045f6b877c05960a688974babc7aead9e28c73abdfb499b0776c5

Tx prefix hash: aeeeffc399887442a64960bd628efad347df0e01ddd1275f8ea40df465824f28
Tx public key: 783100e8dc95f80e12e054a4187e9deca335e01bf48c9198d752d9969a4d30da
Timestamp: 1764668404 Timestamp [UCT]: 2025-12-02 09:40:04 Age [y:d:h:m:s]: 00:057:23:01:02
Block: 1424751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41322 RingCT/type: yes/0
Extra: 01783100e8dc95f80e12e054a4187e9deca335e01bf48c9198d752d9969a4d30da02110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 356aef6fb07c917b20935745dfd991ca8f82bcefa8aac7a380513b0828265e7e 0.600000000000 1913382 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": 1424761, "vin": [ { "gen": { "height": 1424751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "356aef6fb07c917b20935745dfd991ca8f82bcefa8aac7a380513b0828265e7e" } } ], "extra": [ 1, 120, 49, 0, 232, 220, 149, 248, 14, 18, 224, 84, 164, 24, 126, 157, 236, 163, 53, 224, 27, 244, 140, 145, 152, 215, 82, 217, 150, 154, 77, 48, 218, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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