Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8b04ec2f0858d03f8af8be0908b740037266e827d2f05824a86bba96f069771

Tx prefix hash: 65749d1ab8eae1e0ef5c270c4c8486afd8421b45f47a08bbab0908449b706226
Tx public key: 6a581f373ef9e661d8f59c29808bf1a4eba1b7b144241670fb344d184270eda0
Timestamp: 1698773503 Timestamp [UCT]: 2023-10-31 17:31:43 Age [y:d:h:m:s]: 01:162:13:10:48
Block: 881784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377182 RingCT/type: yes/0
Extra: 016a581f373ef9e661d8f59c29808bf1a4eba1b7b144241670fb344d184270eda0021100000005faf35c9c000000000000000000

1 output(s) for total of 0.734993625000 dcy

stealth address amount amount idx
00: 8fe54dabf7fa57efa05336dd8397bbc280ba93a94b2559bcb2ffed1ea3859174 0.734993625000 1337404 of 0

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": 881794, "vin": [ { "gen": { "height": 881784 } } ], "vout": [ { "amount": 734993625, "target": { "key": "8fe54dabf7fa57efa05336dd8397bbc280ba93a94b2559bcb2ffed1ea3859174" } } ], "extra": [ 1, 106, 88, 31, 55, 62, 249, 230, 97, 216, 245, 156, 41, 128, 139, 241, 164, 235, 161, 183, 177, 68, 36, 22, 112, 251, 52, 77, 24, 66, 112, 237, 160, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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