Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387ecfe3080aa65d53887ef458d540b92d0ed1116a9e74b6889e1ba82106b1d3

Tx prefix hash: f53e9794410a46adea2e153a2e5251669448c917b26f38f5e1cefd8fcc61c2c4
Tx public key: 9c26e7d66379ba9a6f163e42763b5cd3de9f9080f55b1ef9f6aeb76974e8d83b
Timestamp: 1701508794 Timestamp [UCT]: 2023-12-02 09:19:54 Age [y:d:h:m:s]: 01:084:05:17:13
Block: 904247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321311 RingCT/type: yes/0
Extra: 019c26e7d66379ba9a6f163e42763b5cd3de9f9080f55b1ef9f6aeb76974e8d83b0211000000014b8f5122000000000000000000

1 output(s) for total of 0.619233289000 dcy

stealth address amount amount idx
00: 6972c02ad3dd10a3f7589a03b3a859a54ece23008ffc849c8bf7146427e9a8c5 0.619233289000 1360962 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": 904257, "vin": [ { "gen": { "height": 904247 } } ], "vout": [ { "amount": 619233289, "target": { "key": "6972c02ad3dd10a3f7589a03b3a859a54ece23008ffc849c8bf7146427e9a8c5" } } ], "extra": [ 1, 156, 38, 231, 214, 99, 121, 186, 154, 111, 22, 62, 66, 118, 59, 92, 211, 222, 159, 144, 128, 245, 91, 30, 249, 246, 174, 183, 105, 116, 232, 216, 59, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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