Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 922e5b13dc2e1503cca47f7ec47597ca413d33d4d705f22672a67971b8c610a6

Tx prefix hash: ffaa17d8956947d3f95b93b4fe520c04253f8bfce5ea5281f2acf4f570326e14
Tx public key: 5064f9fb33fb2c70701e86a5dcb9985ddb5d6990332dbde524b5ad4bc8ae722a
Timestamp: 1710342654 Timestamp [UCT]: 2024-03-13 15:10:54 Age [y:d:h:m:s]: 01:008:05:50:47
Block: 977507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266864 RingCT/type: yes/0
Extra: 015064f9fb33fb2c70701e86a5dcb9985ddb5d6990332dbde524b5ad4bc8ae722a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d0d4c9f3e374e63ffed6d9c181912691bb3d48c8e5c4e7a0a683ca3ca059a4e 0.600000000000 1437510 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": 977517, "vin": [ { "gen": { "height": 977507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d0d4c9f3e374e63ffed6d9c181912691bb3d48c8e5c4e7a0a683ca3ca059a4e" } } ], "extra": [ 1, 80, 100, 249, 251, 51, 251, 44, 112, 112, 30, 134, 165, 220, 185, 152, 93, 219, 93, 105, 144, 51, 45, 189, 229, 36, 181, 173, 75, 200, 174, 114, 42, 2, 17, 0, 0, 0, 4, 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