Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 711c7a7e79c1fa38c11cd622861fbd1994bd55c885914ca24f3d2d9eccea1033

Tx prefix hash: 2f79c33ffd9d28b750cf2166e0a91eb34ee3ef56b406de8c2de8af8a22695ef2
Tx public key: 47078a67d933d1a4a8714ca95a84ea2d1023fc8b821b93532e4b6f05afdb7b56
Timestamp: 1729504209 Timestamp [UCT]: 2024-10-21 09:50:09 Age [y:d:h:m:s]: 01:018:15:03:29
Block: 1136314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271700 RingCT/type: yes/0
Extra: 0147078a67d933d1a4a8714ca95a84ea2d1023fc8b821b93532e4b6f05afdb7b56021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ede6d07361a95863672c77a5f9868b7cc23387ac18f27d216bb46325c40295b8 0.600000000000 1619659 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": 1136324, "vin": [ { "gen": { "height": 1136314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ede6d07361a95863672c77a5f9868b7cc23387ac18f27d216bb46325c40295b8" } } ], "extra": [ 1, 71, 7, 138, 103, 217, 51, 209, 164, 168, 113, 76, 169, 90, 132, 234, 45, 16, 35, 252, 139, 130, 27, 147, 83, 46, 75, 111, 5, 175, 219, 123, 86, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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