Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f944e482539bfc864cffe7ea811c037cdcd4da79f140da9ce97fb0ab9050d303

Tx prefix hash: 89e9489482c76f7a75eae04d4e8c8fcda7acbfdbd93a7d406066f9def81a3a3b
Tx public key: 7521fcc97964e3d4ad66a784fb6627b5f0f7d4c6e3b816c57f8a251c60c5abd7
Timestamp: 1718844266 Timestamp [UCT]: 2024-06-20 00:44:26 Age [y:d:h:m:s]: 00:284:17:40:34
Block: 1047971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203469 RingCT/type: yes/0
Extra: 017521fcc97964e3d4ad66a784fb6627b5f0f7d4c6e3b816c57f8a251c60c5abd70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 764daa77787efd4042717b14b1264e540f9e7630863417d6e6bd330c17c75318 0.600000000000 1517934 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": 1047981, "vin": [ { "gen": { "height": 1047971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "764daa77787efd4042717b14b1264e540f9e7630863417d6e6bd330c17c75318" } } ], "extra": [ 1, 117, 33, 252, 201, 121, 100, 227, 212, 173, 102, 167, 132, 251, 102, 39, 181, 240, 247, 212, 198, 227, 184, 22, 197, 127, 138, 37, 28, 96, 197, 171, 215, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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