Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea21835febc404515ca51a683ddfe722988f7b6a36cdd029291a0fa23e28e84

Tx prefix hash: 6b6f290c87f2efcb3b9e5a1388244ce89866997eca73299d169d7d856a1028f1
Tx public key: 2f734d2deb08d8f0a9fda535c12d3c403e7101e18e7518b4f651d32bf47a8258
Timestamp: 1762400692 Timestamp [UCT]: 2025-11-06 03:44:52 Age [y:d:h:m:s]: 00:088:01:00:12
Block: 1405941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62868 RingCT/type: yes/0
Extra: 012f734d2deb08d8f0a9fda535c12d3c403e7101e18e7518b4f651d32bf47a8258021100000007df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8e10ff9e6facaaa13d9688d7ad6d46c9861442d935747a3f914cfcffa1ee582 0.600000000000 1894322 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": 1405951, "vin": [ { "gen": { "height": 1405941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8e10ff9e6facaaa13d9688d7ad6d46c9861442d935747a3f914cfcffa1ee582" } } ], "extra": [ 1, 47, 115, 77, 45, 235, 8, 216, 240, 169, 253, 165, 53, 193, 45, 60, 64, 62, 113, 1, 225, 142, 117, 24, 180, 246, 81, 211, 43, 244, 122, 130, 88, 2, 17, 0, 0, 0, 7, 223, 90, 36, 122, 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