Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 473315e9e47e1871382dbcda0763d888c5cd3f5660e4d88d1f93107168893846

Tx prefix hash: e317bd1cf095def3162ff919ef31068c2785eff5db0317083a5b8ec77528868e
Tx public key: 7575a4e51a69e026f5a48ed5c0ab93a02e6a48987d31bc8d201001dbd27beb14
Timestamp: 1704625073 Timestamp [UCT]: 2024-01-07 10:57:53 Age [y:d:h:m:s]: 01:078:17:09:32
Block: 930070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317355 RingCT/type: yes/0
Extra: 017575a4e51a69e026f5a48ed5c0ab93a02e6a48987d31bc8d201001dbd27beb1402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6797376a9cf7639fc0abf512a6d6f711c11b8b6d82c0f50e96f6dfeb2c12d7c 0.600000000000 1387948 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": 930080, "vin": [ { "gen": { "height": 930070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6797376a9cf7639fc0abf512a6d6f711c11b8b6d82c0f50e96f6dfeb2c12d7c" } } ], "extra": [ 1, 117, 117, 164, 229, 26, 105, 224, 38, 245, 164, 142, 213, 192, 171, 147, 160, 46, 106, 72, 152, 125, 49, 188, 141, 32, 16, 1, 219, 210, 123, 235, 20, 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