Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b3e21566da50c48a6839e58de629afc64087417e6e5c9269e3181595abf986d

Tx prefix hash: 77e0b29d3a5d2588aeecaf314b5dfcda21f64eb7847093242aee3eeffc99d863
Tx public key: fb1c8fc5a76cd84cead6ebf7a7550abd32320e2afd14e4cbeaed012fc9dee535
Timestamp: 1737998692 Timestamp [UCT]: 2025-01-27 17:24:52 Age [y:d:h:m:s]: 00:322:18:21:49
Block: 1206379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228458 RingCT/type: yes/0
Extra: 01fb1c8fc5a76cd84cead6ebf7a7550abd32320e2afd14e4cbeaed012fc9dee5350211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 942c81bfa71cbbc378af168b20834c67e3f5d2a63e0230880380f08729b57efb 0.600000000000 1693084 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": 1206389, "vin": [ { "gen": { "height": 1206379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "942c81bfa71cbbc378af168b20834c67e3f5d2a63e0230880380f08729b57efb" } } ], "extra": [ 1, 251, 28, 143, 197, 167, 108, 216, 76, 234, 214, 235, 247, 167, 85, 10, 189, 50, 50, 14, 42, 253, 20, 228, 203, 234, 237, 1, 47, 201, 222, 229, 53, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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