Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cadfd469feb9d7b832cae37c297d0d7c4d73c7458dfe34784c561e87b17e287c

Tx prefix hash: 98d7443604acbf2732392b62babf15c1547119d8bcf1bb3ecc0118eac90f3208
Tx public key: 700165477776df5f06b261f6146d0ce6c65ca758ef1a100998aba2e4e6820f3e
Timestamp: 1681078547 Timestamp [UCT]: 2023-04-09 22:15:47 Age [y:d:h:m:s]: 01:363:12:30:28
Block: 735116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521091 RingCT/type: yes/0
Extra: 01700165477776df5f06b261f6146d0ce6c65ca758ef1a100998aba2e4e6820f3e021100000006b3164c24000000000000000000

1 output(s) for total of 2.250379463000 dcy

stealth address amount amount idx
00: 626eb9f87df23f60e208bb732e36ec4a654daf9a70d2fb8b054673df3a3f08ad 2.250379463000 1181407 of 0

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": 735126, "vin": [ { "gen": { "height": 735116 } } ], "vout": [ { "amount": 2250379463, "target": { "key": "626eb9f87df23f60e208bb732e36ec4a654daf9a70d2fb8b054673df3a3f08ad" } } ], "extra": [ 1, 112, 1, 101, 71, 119, 118, 223, 95, 6, 178, 97, 246, 20, 109, 12, 230, 198, 92, 167, 88, 239, 26, 16, 9, 152, 171, 162, 228, 230, 130, 15, 62, 2, 17, 0, 0, 0, 6, 179, 22, 76, 36, 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