Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ceb52961d889d6c847a306a536f9626788182b0cecb7e175b0f90096c729210

Tx prefix hash: 9daae3b4fab81f505235fbeaead4f1f5f3a2b85e5e6bb01fb47215c34f0119e1
Tx public key: 7ec9056980e1a9202aca3c3c4c135be13872ebf208d56490fac30a60b89158d7
Timestamp: 1711343951 Timestamp [UCT]: 2024-03-25 05:19:11 Age [y:d:h:m:s]: 00:363:00:43:50
Block: 985814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259542 RingCT/type: yes/0
Extra: 017ec9056980e1a9202aca3c3c4c135be13872ebf208d56490fac30a60b89158d70211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99ecd719dd51db6c0d2ae27523cd0a1ce73f75f55a40e2d64f0daa7728dffea4 0.600000000000 1446035 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": 985824, "vin": [ { "gen": { "height": 985814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99ecd719dd51db6c0d2ae27523cd0a1ce73f75f55a40e2d64f0daa7728dffea4" } } ], "extra": [ 1, 126, 201, 5, 105, 128, 225, 169, 32, 42, 202, 60, 60, 76, 19, 91, 225, 56, 114, 235, 242, 8, 213, 100, 144, 250, 195, 10, 96, 184, 145, 88, 215, 2, 17, 0, 0, 0, 7, 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