Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1129f3d47d07f5d6f31252cad0f774b6933a03e80bbab6f239426f541331d904

Tx prefix hash: ffaa5bcb2c336f06fafeae9b26ae21929e8f6e64652cda176a663cdf33bb5c0e
Tx public key: 78bfd8fba42b22dad6c26565d5d35ca1aeb334049d0bce9875e46a7c28186188
Timestamp: 1674011095 Timestamp [UCT]: 2023-01-18 03:04:55 Age [y:d:h:m:s]: 02:001:15:23:13
Block: 677143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523034 RingCT/type: yes/0
Extra: 0178bfd8fba42b22dad6c26565d5d35ca1aeb334049d0bce9875e46a7c281861880211000000038b7b6602000000000000000000

1 output(s) for total of 3.502225391000 dcy

stealth address amount amount idx
00: aa6281d23247d85350aa8690fc6299abdfffbab6eba2275ddee453cd1262a0d1 3.502225391000 1118910 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": 677153, "vin": [ { "gen": { "height": 677143 } } ], "vout": [ { "amount": 3502225391, "target": { "key": "aa6281d23247d85350aa8690fc6299abdfffbab6eba2275ddee453cd1262a0d1" } } ], "extra": [ 1, 120, 191, 216, 251, 164, 43, 34, 218, 214, 194, 101, 101, 213, 211, 92, 161, 174, 179, 52, 4, 157, 11, 206, 152, 117, 228, 106, 124, 40, 24, 97, 136, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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