Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f699d7006c91261ad67f905efd852d4a3d7a5a8525c8f43e91a673d26674fb13

Tx prefix hash: eea7fe47f8201c553b6182392fb5c51ce9ba49cf6fafb613b2d8b8685e3071c1
Tx public key: 03c15830cee9a914d7bc480880cdabcdb63ddecee6755db45044c2229b7379f7
Timestamp: 1683632391 Timestamp [UCT]: 2023-05-09 11:39:51 Age [y:d:h:m:s]: 01:248:01:27:13
Block: 756310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438728 RingCT/type: yes/0
Extra: 0103c15830cee9a914d7bc480880cdabcdb63ddecee6755db45044c2229b7379f7021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.914393472000 dcy

stealth address amount amount idx
00: 7a0dc0af0e9fb052e63454253fc5d8a213ba1fe6e367bd03fc60932a87dd23e8 1.914393472000 1204671 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": 756320, "vin": [ { "gen": { "height": 756310 } } ], "vout": [ { "amount": 1914393472, "target": { "key": "7a0dc0af0e9fb052e63454253fc5d8a213ba1fe6e367bd03fc60932a87dd23e8" } } ], "extra": [ 1, 3, 193, 88, 48, 206, 233, 169, 20, 215, 188, 72, 8, 128, 205, 171, 205, 182, 61, 222, 206, 230, 117, 93, 180, 80, 68, 194, 34, 155, 115, 121, 247, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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