Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad136fbd4c79260341d1bf2d4cddafd51bd3e523b664dbf2a0aa15388964e969

Tx prefix hash: b996b4aff3b3d4d65f3ba9ec5d2710685b6dabd96a8706c26beb89a66ed48f7c
Tx public key: 10a75821b1a3994ab7e97b1db9e861a0ef1af2edc6290469bded902cd87aa6de
Timestamp: 1716689365 Timestamp [UCT]: 2024-05-26 02:09:25 Age [y:d:h:m:s]: 00:299:22:58:06
Block: 1030110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214384 RingCT/type: yes/0
Extra: 0110a75821b1a3994ab7e97b1db9e861a0ef1af2edc6290469bded902cd87aa6de02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1cbf465f1ff441dbb960ef9148f75925464ca7b63d87580fd77a022a08d9a69 0.600000000000 1498363 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": 1030120, "vin": [ { "gen": { "height": 1030110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1cbf465f1ff441dbb960ef9148f75925464ca7b63d87580fd77a022a08d9a69" } } ], "extra": [ 1, 16, 167, 88, 33, 177, 163, 153, 74, 183, 233, 123, 29, 185, 232, 97, 160, 239, 26, 242, 237, 198, 41, 4, 105, 189, 237, 144, 44, 216, 122, 166, 222, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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