Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96775accdf66272e32ca39ab8f47fa5ebf74ed31bb0c87d328534dc57c4fe2b

Tx prefix hash: 60778d44847a9c3b1697e869a4e62fdffb030f65c692167ad67d02985a567672
Tx public key: ae0d13aae5743e83b94be8e39962fd32beefbe0918c4d570f3af3f57ccd67270
Timestamp: 1731872069 Timestamp [UCT]: 2024-11-17 19:34:29 Age [y:d:h:m:s]: 00:163:23:24:47
Block: 1155894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117013 RingCT/type: yes/0
Extra: 01ae0d13aae5743e83b94be8e39962fd32beefbe0918c4d570f3af3f57ccd67270021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff22aca403c2806f8c3d4ebf035e8319a7e1a434a9afc40f68e9ea08ef47abac 0.600000000000 1641513 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": 1155904, "vin": [ { "gen": { "height": 1155894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff22aca403c2806f8c3d4ebf035e8319a7e1a434a9afc40f68e9ea08ef47abac" } } ], "extra": [ 1, 174, 13, 19, 170, 229, 116, 62, 131, 185, 75, 232, 227, 153, 98, 253, 50, 190, 239, 190, 9, 24, 196, 213, 112, 243, 175, 63, 87, 204, 214, 114, 112, 2, 17, 0, 0, 0, 1, 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