Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed23cbf3ee015acde463552a5f6fe03eea9e0aae0599240102840d6f7a1fb32

Tx prefix hash: f79357ebd653bfb86aa47e4ed5d3833909a315233fb2e45d7efc3f2908e2d92a
Tx public key: 9f9d0b19c295fb7289a600c781cf41a39fb496917b32e569146668a635e578a2
Timestamp: 1722748099 Timestamp [UCT]: 2024-08-04 05:08:19 Age [y:d:h:m:s]: 00:301:11:49:29
Block: 1080341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215414 RingCT/type: yes/0
Extra: 019f9d0b19c295fb7289a600c781cf41a39fb496917b32e569146668a635e578a202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 906af734d5f922bd55bf58d1fe5153c91faeeb6349e62fb95044f5d7cbedb7cb 0.600000000000 1553652 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": 1080351, "vin": [ { "gen": { "height": 1080341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "906af734d5f922bd55bf58d1fe5153c91faeeb6349e62fb95044f5d7cbedb7cb" } } ], "extra": [ 1, 159, 157, 11, 25, 194, 149, 251, 114, 137, 166, 0, 199, 129, 207, 65, 163, 159, 180, 150, 145, 123, 50, 229, 105, 20, 102, 104, 166, 53, 229, 120, 162, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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