Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 748b160bf42ad5bacca2dd3f1c4ebb2575af826da54d5ac52a54ddab58db6a8c

Tx prefix hash: 453f60b17289762b5a97055b0e4724461c26cea45cf8f3c5e32c777ec3101690
Tx public key: c3247f3583c4e56c4d5dfc87ab62cab88b41c23e2942a8d3accf25a9c2d9336e
Timestamp: 1702678414 Timestamp [UCT]: 2023-12-15 22:13:34 Age [y:d:h:m:s]: 01:035:18:03:01
Block: 913947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286878 RingCT/type: yes/0
Extra: 01c3247f3583c4e56c4d5dfc87ab62cab88b41c23e2942a8d3accf25a9c2d9336e02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bc528044a3a81e5f3d3f6448c939ed75da36c91494298662ce23c79312a7569 0.600000000000 1371227 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": 913957, "vin": [ { "gen": { "height": 913947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bc528044a3a81e5f3d3f6448c939ed75da36c91494298662ce23c79312a7569" } } ], "extra": [ 1, 195, 36, 127, 53, 131, 196, 229, 108, 77, 93, 252, 135, 171, 98, 202, 184, 139, 65, 194, 62, 41, 66, 168, 211, 172, 207, 37, 169, 194, 217, 51, 110, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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