Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb3ef9739ede9d17385f518d071b1eb7f20e8dccd90c86a07abafd2b67afe342

Tx prefix hash: 42ad254546d5337907fb00dc62b2949cfa8958dd0d468f1ead62c65f05de00fa
Tx public key: be10abd98b961d5c2f629c8717cce7f04bfc8b3d58427794a35bc4f5ba2bcb31
Timestamp: 1725199745 Timestamp [UCT]: 2024-09-01 14:09:05 Age [y:d:h:m:s]: 00:129:14:37:29
Block: 1100668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92691 RingCT/type: yes/0
Extra: 01be10abd98b961d5c2f629c8717cce7f04bfc8b3d58427794a35bc4f5ba2bcb31021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa97281eb60503886208fb4d81369690879a4a0f6a5ea481d9c5dcb8004041a 0.600000000000 1576647 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": 1100678, "vin": [ { "gen": { "height": 1100668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa97281eb60503886208fb4d81369690879a4a0f6a5ea481d9c5dcb8004041a" } } ], "extra": [ 1, 190, 16, 171, 217, 139, 150, 29, 92, 47, 98, 156, 135, 23, 204, 231, 240, 75, 252, 139, 61, 88, 66, 119, 148, 163, 91, 196, 245, 186, 43, 203, 49, 2, 17, 0, 0, 0, 5, 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