Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76a5e2707dd3896b1d1dbe8d8b6b7168f2f9e27a996b0026ad4382425aa2db6

Tx prefix hash: 0472ef1e9eaee621511390472c5e48f0df0fabccb3bae7e72163c9d8280a2e0d
Tx public key: 6ec4faf9c7b9c1725f1ab9cb021aa1821e40ca32095390e76f05004b54ea39b5
Timestamp: 1729176509 Timestamp [UCT]: 2024-10-17 14:48:29 Age [y:d:h:m:s]: 00:207:10:37:35
Block: 1133635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148056 RingCT/type: yes/0
Extra: 016ec4faf9c7b9c1725f1ab9cb021aa1821e40ca32095390e76f05004b54ea39b5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b1dbe82ee725c60dd91e2902d0a0ab285b1501ca958c0f8a19c0610ad11a1cc 0.600000000000 1616814 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": 1133645, "vin": [ { "gen": { "height": 1133635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b1dbe82ee725c60dd91e2902d0a0ab285b1501ca958c0f8a19c0610ad11a1cc" } } ], "extra": [ 1, 110, 196, 250, 249, 199, 185, 193, 114, 95, 26, 185, 203, 2, 26, 161, 130, 30, 64, 202, 50, 9, 83, 144, 231, 111, 5, 0, 75, 84, 234, 57, 181, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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