Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e7381e9168892f14b0c2a4fabc4c417c68d509927d37623f4536c94d91b077

Tx prefix hash: f4e3c304e53f10d3f45040cd1b1a4b9073215705d161645d6f9c7102e5febd4f
Tx public key: fb8c6f57e7b54de0f7910e4127339559629b30de5f5da414e0abf2840023de67
Timestamp: 1705474305 Timestamp [UCT]: 2024-01-17 06:51:45 Age [y:d:h:m:s]: 01:292:00:41:26
Block: 937109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467530 RingCT/type: yes/0
Extra: 01fb8c6f57e7b54de0f7910e4127339559629b30de5f5da414e0abf2840023de6702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57323a7ac9b748d4acf4087cd363b6dce916cb20154780a1c0b61797176cc426 0.600000000000 1395153 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": 937119, "vin": [ { "gen": { "height": 937109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57323a7ac9b748d4acf4087cd363b6dce916cb20154780a1c0b61797176cc426" } } ], "extra": [ 1, 251, 140, 111, 87, 231, 181, 77, 224, 247, 145, 14, 65, 39, 51, 149, 89, 98, 155, 48, 222, 95, 93, 164, 20, 224, 171, 242, 132, 0, 35, 222, 103, 2, 17, 0, 0, 0, 4, 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