Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcadfb40fd5172c9733b68bebf75ccb80fc7188128c2a970ee69e337ce632532

Tx prefix hash: 7d6b3b0c266ad6877954bd0f67c6086b530a5e5e2a6c647b78b40a68df2f641f
Tx public key: 1d026c1c5cc4c6084d0998ddfba99a966e41a735217e8accb329f054aea65775
Timestamp: 1760857667 Timestamp [UCT]: 2025-10-19 07:07:47 Age [y:d:h:m:s]: 00:040:02:26:50
Block: 1393181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28704 RingCT/type: yes/0
Extra: 011d026c1c5cc4c6084d0998ddfba99a966e41a735217e8accb329f054aea657750211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd526f97ed6c51b828944850bb4574573e9843cfb3ae5eae2fa5784fbef16c74 0.600000000000 1881440 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": 1393191, "vin": [ { "gen": { "height": 1393181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd526f97ed6c51b828944850bb4574573e9843cfb3ae5eae2fa5784fbef16c74" } } ], "extra": [ 1, 29, 2, 108, 28, 92, 196, 198, 8, 77, 9, 152, 221, 251, 169, 154, 150, 110, 65, 167, 53, 33, 126, 138, 204, 179, 41, 240, 84, 174, 166, 87, 117, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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