Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cddba50bc79cd2193418ff7cd09b9be8dee636254b61b2b1413713f465796d36

Tx prefix hash: fae838a1215f8a4aebad2a9a343fd976cdd86ea46826b95d639938f4c6be72a9
Tx public key: f2a7a51da509bece8c5e44e92a90e710c995d8cff31dc545549b7138325328b6
Timestamp: 1736190650 Timestamp [UCT]: 2025-01-06 19:10:50 Age [y:d:h:m:s]: 00:164:11:15:07
Block: 1191644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117237 RingCT/type: yes/0
Extra: 01f2a7a51da509bece8c5e44e92a90e710c995d8cff31dc545549b7138325328b6021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 815396c7ccfab528db361e4a5aca56ce354874315a4eeb1e024f463e52d4653d 0.600000000000 1678185 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": 1191654, "vin": [ { "gen": { "height": 1191644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "815396c7ccfab528db361e4a5aca56ce354874315a4eeb1e024f463e52d4653d" } } ], "extra": [ 1, 242, 167, 165, 29, 165, 9, 190, 206, 140, 94, 68, 233, 42, 144, 231, 16, 201, 149, 216, 207, 243, 29, 197, 69, 84, 155, 113, 56, 50, 83, 40, 182, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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