Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ae7e7e6fc05dccf66728540a85191f528dc7e0789c636db951890897c1303c

Tx prefix hash: bfc22f23f69f593967eed9eecd4cd883064ceae49e7a6e098ce4b1e9ecf686fe
Tx public key: a80a954db3266e50e4de195a115f29ffe928b3eab52a4bfb6a0c1cde9b24a41a
Timestamp: 1754929046 Timestamp [UCT]: 2025-08-11 16:17:26 Age [y:d:h:m:s]: 00:013:03:40:51
Block: 1344923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8717 RingCT/type: yes/0
Extra: 01a80a954db3266e50e4de195a115f29ffe928b3eab52a4bfb6a0c1cde9b24a41a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a2f701828921da7565527981b0df4fd5e619e859e50db4abaa246242f3779ca 0.600000000000 1832810 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": 1344933, "vin": [ { "gen": { "height": 1344923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a2f701828921da7565527981b0df4fd5e619e859e50db4abaa246242f3779ca" } } ], "extra": [ 1, 168, 10, 149, 77, 179, 38, 110, 80, 228, 222, 25, 90, 17, 95, 41, 255, 233, 40, 179, 234, 181, 42, 75, 251, 106, 12, 28, 222, 155, 36, 164, 26, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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