Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ad8ed3cc08ef5597d20d763341446c476eadf29c7d7a686d67eeb224f1acc5c

Tx prefix hash: c5d4aa4d3e1b72c4f7ef929e02d2d95645269ae07b2137d81b56d90f6833d0b5
Tx public key: 438d21be8be4f4c589cf7c778bbdd75097f5a7fe372409a1f294213730af7e15
Timestamp: 1712719359 Timestamp [UCT]: 2024-04-10 03:22:39 Age [y:d:h:m:s]: 01:051:02:00:37
Block: 997174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297523 RingCT/type: yes/0
Extra: 01438d21be8be4f4c589cf7c778bbdd75097f5a7fe372409a1f294213730af7e1502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e85ce8aac15c78306357116cc8d5e2a9493391d4f7312a103edce50c433bae4e 0.600000000000 1457604 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": 997184, "vin": [ { "gen": { "height": 997174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e85ce8aac15c78306357116cc8d5e2a9493391d4f7312a103edce50c433bae4e" } } ], "extra": [ 1, 67, 141, 33, 190, 139, 228, 244, 197, 137, 207, 124, 119, 139, 189, 215, 80, 151, 245, 167, 254, 55, 36, 9, 161, 242, 148, 33, 55, 48, 175, 126, 21, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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