Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f7eb4631d521da4d7d2498195db0db6eaee592f244a0c1df3eb16d3dd6fd28

Tx prefix hash: b299d60cc0d08634d690a6e9b2b2af7bc1ee5b6b7af018deda984aab179c1568
Tx public key: f258f98d0089d568b9f855acb0cf31d363b18a0fe5ef2ed110bee08515371566
Timestamp: 1761682124 Timestamp [UCT]: 2025-10-28 20:08:44 Age [y:d:h:m:s]: 00:056:06:14:14
Block: 1400013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40263 RingCT/type: yes/0
Extra: 01f258f98d0089d568b9f855acb0cf31d363b18a0fe5ef2ed110bee0851537156602110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1169d8f21d19e57c4c8f2328f329c5deedef5fc746aa07d9dfe161bc1e6419b9 0.600000000000 1888320 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": 1400023, "vin": [ { "gen": { "height": 1400013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1169d8f21d19e57c4c8f2328f329c5deedef5fc746aa07d9dfe161bc1e6419b9" } } ], "extra": [ 1, 242, 88, 249, 141, 0, 137, 213, 104, 185, 248, 85, 172, 176, 207, 49, 211, 99, 177, 138, 15, 229, 239, 46, 209, 16, 190, 224, 133, 21, 55, 21, 102, 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