Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ce028d706ec54d4520e255f1e36c8b48ce440c915a85554792fa46e4895b87

Tx prefix hash: 3f3af4bab40c00e76c3de33375434a25b86d34661c2c7dc6adad5770c5b5abc7
Tx public key: ffb1a249164fa06269e39948111fed6e9a5e07332e83fa6999b7f38f33404197
Timestamp: 1727091114 Timestamp [UCT]: 2024-09-23 11:31:54 Age [y:d:h:m:s]: 00:065:23:46:27
Block: 1116347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47166 RingCT/type: yes/0
Extra: 01ffb1a249164fa06269e39948111fed6e9a5e07332e83fa6999b7f38f33404197021100000011e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: ac3d489f855398c6a3ceeaa8147e8acf0b33fae2d4ff8b51d5749efdc3a22b73 0.608000000000 1596794 of 0

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": 1116357, "vin": [ { "gen": { "height": 1116347 } } ], "vout": [ { "amount": 608000000, "target": { "key": "ac3d489f855398c6a3ceeaa8147e8acf0b33fae2d4ff8b51d5749efdc3a22b73" } } ], "extra": [ 1, 255, 177, 162, 73, 22, 79, 160, 98, 105, 227, 153, 72, 17, 31, 237, 110, 154, 94, 7, 51, 46, 131, 250, 105, 153, 183, 243, 143, 51, 64, 65, 151, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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