Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f1caddd6e2affddec72d6e073d95d30c5fda55f796d940cf422e738c38849a

Tx prefix hash: c4d0b69aff3cdffeef58fc540aacd4b87f0febcc7d3626f134ae512875d97545
Tx public key: 3c4084611c43901b1a85753ed72e0d859b052b8630fdf2ce2079a767714e5a40
Timestamp: 1745863407 Timestamp [UCT]: 2025-04-28 18:03:27 Age [y:d:h:m:s]: 00:011:02:41:17
Block: 1271468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7933 RingCT/type: yes/0
Extra: 013c4084611c43901b1a85753ed72e0d859b052b8630fdf2ce2079a767714e5a4002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c6141d5be7bad6d48bfbfae62a33ed811728ce7ec4e364285e6114bf35eb9e5 0.600000000000 1758729 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": 1271478, "vin": [ { "gen": { "height": 1271468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c6141d5be7bad6d48bfbfae62a33ed811728ce7ec4e364285e6114bf35eb9e5" } } ], "extra": [ 1, 60, 64, 132, 97, 28, 67, 144, 27, 26, 133, 117, 62, 215, 46, 13, 133, 155, 5, 43, 134, 48, 253, 242, 206, 32, 121, 167, 103, 113, 78, 90, 64, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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