Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb13f3f6d470278d39ca7f8343ed269c203be7532d6dfef8dc37e0d2242bd1bb

Tx prefix hash: 6924d82d65719fd470ce0676c883bdd90e4e0310203550164a8c598d76b75258
Tx public key: 75878d3f8014e87b7cbe38f66032d5be0ba8311888ef62d1f59f60620b02e2d3
Timestamp: 1758030150 Timestamp [UCT]: 2025-09-16 13:42:30 Age [y:d:h:m:s]: 00:135:00:21:58
Block: 1369740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96484 RingCT/type: yes/0
Extra: 0175878d3f8014e87b7cbe38f66032d5be0ba8311888ef62d1f59f60620b02e2d3021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6decd53feadca0e73f5ada6d41bbd6c98cf2ebea8c4ae2c34ab43341dcaf4e5c 0.600000000000 1857815 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": 1369750, "vin": [ { "gen": { "height": 1369740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6decd53feadca0e73f5ada6d41bbd6c98cf2ebea8c4ae2c34ab43341dcaf4e5c" } } ], "extra": [ 1, 117, 135, 141, 63, 128, 20, 232, 123, 124, 190, 56, 246, 96, 50, 213, 190, 11, 168, 49, 24, 136, 239, 98, 209, 245, 159, 96, 98, 11, 2, 226, 211, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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