Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8616e53a04b50bb14d114cd567ec9839b8ee2108f0fa480a580e031ac745714

Tx prefix hash: 3a5b7bdf6a513bbe0049c94ca7d2265c324777e814a893a28605c7d91bde41c9
Tx public key: fbd0ae810d19370a70673c0974e84db37329b44ded6e09a811fdda3ab2c511b9
Timestamp: 1730820673 Timestamp [UCT]: 2024-11-05 15:31:13 Age [y:d:h:m:s]: 00:001:17:06:08
Block: 1147177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1232 RingCT/type: yes/0
Extra: 01fbd0ae810d19370a70673c0974e84db37329b44ded6e09a811fdda3ab2c511b90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c2896260b4c27f91f82ea07f30ddd00c07245679be0f72c5a0571f34518c1b0 0.600000000000 1631870 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": 1147187, "vin": [ { "gen": { "height": 1147177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c2896260b4c27f91f82ea07f30ddd00c07245679be0f72c5a0571f34518c1b0" } } ], "extra": [ 1, 251, 208, 174, 129, 13, 25, 55, 10, 112, 103, 60, 9, 116, 232, 77, 179, 115, 41, 180, 77, 237, 110, 9, 168, 17, 253, 218, 58, 178, 197, 17, 185, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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