Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1213408378f96461d9edc583fa8fb7ab6ca1c9e449416c82a45a478b17a42394

Tx prefix hash: 102d763f3cc76d41bfd5eeda3db0fa3e1acb0863749ed71aa6edb0f3ae8693cb
Tx public key: 834a5a51a776e84459f50bfb71062a2c13cab06b7012986ea11a7434ef920ac5
Timestamp: 1733635302 Timestamp [UCT]: 2024-12-08 05:21:42 Age [y:d:h:m:s]: 00:124:03:23:13
Block: 1170501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88522 RingCT/type: yes/0
Extra: 01834a5a51a776e84459f50bfb71062a2c13cab06b7012986ea11a7434ef920ac5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 552327c297ffd9b12ded2211db3cb8b12d2e56f0ebf26f39970243f2c2b63bd7 0.600000000000 1656232 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": 1170511, "vin": [ { "gen": { "height": 1170501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "552327c297ffd9b12ded2211db3cb8b12d2e56f0ebf26f39970243f2c2b63bd7" } } ], "extra": [ 1, 131, 74, 90, 81, 167, 118, 232, 68, 89, 245, 11, 251, 113, 6, 42, 44, 19, 202, 176, 107, 112, 18, 152, 110, 161, 26, 116, 52, 239, 146, 10, 197, 2, 17, 0, 0, 0, 4, 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