Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01d018d2fa9bd5f074fdc48922895e78e1635011c584bb5dc963407097016e0

Tx prefix hash: 5c237ef9745db06152adca1c2f031ae719769e3599b8c2e430dd5142772887cb
Tx public key: 274adbd929c1bf47fba7fa3f6d4bcddf3353d214013e86c5cfe9fa4420228e13
Timestamp: 1709851313 Timestamp [UCT]: 2024-03-07 22:41:53 Age [y:d:h:m:s]: 01:055:07:16:01
Block: 973426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300530 RingCT/type: yes/0
Extra: 01274adbd929c1bf47fba7fa3f6d4bcddf3353d214013e86c5cfe9fa4420228e1302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fd9eef4eacde2a5317a917db33a67b6e5828d1cacb2475e8d21a6b90706d56a 0.600000000000 1433361 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": 973436, "vin": [ { "gen": { "height": 973426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fd9eef4eacde2a5317a917db33a67b6e5828d1cacb2475e8d21a6b90706d56a" } } ], "extra": [ 1, 39, 74, 219, 217, 41, 193, 191, 71, 251, 167, 250, 63, 109, 75, 205, 223, 51, 83, 210, 20, 1, 62, 134, 197, 207, 233, 250, 68, 32, 34, 142, 19, 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