Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85b2e00d84ed86377970b280bb4803d81d4eae9554847b6f5966e7f487a45c47

Tx prefix hash: dc7ca0d67dc284b6d4672bd6fc6c33946ea3a105d146bb9969e7559d14fad37a
Tx public key: ba4952c4c85e5c21556067e5894a29e01d9949c40ac012b9b338d1768e25428c
Timestamp: 1731773201 Timestamp [UCT]: 2024-11-16 16:06:41 Age [y:d:h:m:s]: 00:188:01:01:10
Block: 1155058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134266 RingCT/type: yes/0
Extra: 01ba4952c4c85e5c21556067e5894a29e01d9949c40ac012b9b338d1768e25428c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a69dc86e2ba5583e8dd896eef8d4a239daa7bd3816cac39c7577f1014f61145 0.600000000000 1640671 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": 1155068, "vin": [ { "gen": { "height": 1155058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a69dc86e2ba5583e8dd896eef8d4a239daa7bd3816cac39c7577f1014f61145" } } ], "extra": [ 1, 186, 73, 82, 196, 200, 94, 92, 33, 85, 96, 103, 229, 137, 74, 41, 224, 29, 153, 73, 196, 10, 192, 18, 185, 179, 56, 209, 118, 142, 37, 66, 140, 2, 17, 0, 0, 0, 4, 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