Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786e5c8f4721cc0b40ff22996c35e1d6e788a07794006cfb291579e3af26b8e3

Tx prefix hash: 56066dad7be48f565f2d9cb8b3a37072ee7251c9676439234f4392c564a08d1e
Tx public key: b81297aa0ce04948c43ad080b26e894d42f0d4ca63e880f3b27a444bd975a6f0
Timestamp: 1761552599 Timestamp [UCT]: 2025-10-27 08:09:59 Age [y:d:h:m:s]: 00:016:01:41:37
Block: 1398941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11491 RingCT/type: yes/0
Extra: 01b81297aa0ce04948c43ad080b26e894d42f0d4ca63e880f3b27a444bd975a6f002110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa8b3735860bf292bfe27a83aced23b599eadcc797901dec3cb6ebde7061dff2 0.600000000000 1887244 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": 1398951, "vin": [ { "gen": { "height": 1398941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa8b3735860bf292bfe27a83aced23b599eadcc797901dec3cb6ebde7061dff2" } } ], "extra": [ 1, 184, 18, 151, 170, 12, 224, 73, 72, 196, 58, 208, 128, 178, 110, 137, 77, 66, 240, 212, 202, 99, 232, 128, 243, 178, 122, 68, 75, 217, 117, 166, 240, 2, 17, 0, 0, 0, 4, 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