Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 302c739a1df42f2cd370ddc2bd58405581b779e6f4d66b4d4014306d2ec2c5f7

Tx prefix hash: 24b722e6047c06a167ff922d848927eb420f20674eedf3e5eac83375e84d9f65
Tx public key: ee5fbda6f7e3625da3a9a7ee88617f8e690ca6576eb846297d70023ead204dff
Timestamp: 1673990908 Timestamp [UCT]: 2023-01-17 21:28:28 Age [y:d:h:m:s]: 02:003:15:30:55
Block: 676979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524450 RingCT/type: yes/0
Extra: 01ee5fbda6f7e3625da3a9a7ee88617f8e690ca6576eb846297d70023ead204dff02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.506610207000 dcy

stealth address amount amount idx
00: e4a50d35a74998113a49a58b2c249e5bb5778947d8abfaeaaea6e9395ed93c88 3.506610207000 1118736 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": 676989, "vin": [ { "gen": { "height": 676979 } } ], "vout": [ { "amount": 3506610207, "target": { "key": "e4a50d35a74998113a49a58b2c249e5bb5778947d8abfaeaaea6e9395ed93c88" } } ], "extra": [ 1, 238, 95, 189, 166, 247, 227, 98, 93, 163, 169, 167, 238, 136, 97, 127, 142, 105, 12, 166, 87, 110, 184, 70, 41, 125, 112, 2, 62, 173, 32, 77, 255, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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