Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d273b4c8ccae5ae02338d953895d223f64f61b2efe23bbe8c4744d7d7ededc9b

Tx prefix hash: c0a7555299d7c37053990372dffd5366a92831f1b4b6e09e622d2ac9141feb89
Tx public key: b4780369ecbfc6892e66dea8d9db50c4bb53f82e3be951767e75aaf6bc39eefb
Timestamp: 1735642505 Timestamp [UCT]: 2024-12-31 10:55:05 Age [y:d:h:m:s]: 00:303:19:05:45
Block: 1187111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214625 RingCT/type: yes/0
Extra: 01b4780369ecbfc6892e66dea8d9db50c4bb53f82e3be951767e75aaf6bc39eefb0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d650294173ce9b6efcb1ddc25e4cee62506029ba62f4b6fe826494440d40297 0.600000000000 1673598 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": 1187121, "vin": [ { "gen": { "height": 1187111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d650294173ce9b6efcb1ddc25e4cee62506029ba62f4b6fe826494440d40297" } } ], "extra": [ 1, 180, 120, 3, 105, 236, 191, 198, 137, 46, 102, 222, 168, 217, 219, 80, 196, 187, 83, 248, 46, 59, 233, 81, 118, 126, 117, 170, 246, 188, 57, 238, 251, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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