Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00c7e039cb1cebf8a4349082e00cf53e69f2ac9c5f52e381bf00b1284c72413

Tx prefix hash: f4ad91d52ae172560d70be772c5cb537f054e0715c0697de610178d0ea8bf040
Tx public key: 4c7227b635fd21b8b90f23c778e7d4fae92039893164cefd618af5f2d4065108
Timestamp: 1719921140 Timestamp [UCT]: 2024-07-02 11:52:20 Age [y:d:h:m:s]: 00:277:07:56:25
Block: 1056905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198150 RingCT/type: yes/0
Extra: 014c7227b635fd21b8b90f23c778e7d4fae92039893164cefd618af5f2d40651080211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1ef7faaf56c91920d5d150a0c139e7a5d78f7013153dbcea957ba6269f1a910 0.600000000000 1527334 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": 1056915, "vin": [ { "gen": { "height": 1056905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1ef7faaf56c91920d5d150a0c139e7a5d78f7013153dbcea957ba6269f1a910" } } ], "extra": [ 1, 76, 114, 39, 182, 53, 253, 33, 184, 185, 15, 35, 199, 120, 231, 212, 250, 233, 32, 57, 137, 49, 100, 206, 253, 97, 138, 245, 242, 212, 6, 81, 8, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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