Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69b7a75fc7fa8e0214f8399484516186f90f32b13b11061ceee771af62ef0cbd

Tx prefix hash: f1f77f4025c56163d13e2f6bc95e59b03c57ed91b2cd56078c283499114726be
Tx public key: 7213df83d815914f5318f1da1f246e857bdcc641c61c52b0b5407a2fba4e21d7
Timestamp: 1699804165 Timestamp [UCT]: 2023-11-12 15:49:25 Age [y:d:h:m:s]: 01:163:20:21:33
Block: 890129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378296 RingCT/type: yes/0
Extra: 017213df83d815914f5318f1da1f246e857bdcc641c61c52b0b5407a2fba4e21d7021100000003faf35c9c000000000000000000

1 output(s) for total of 0.689656940000 dcy

stealth address amount amount idx
00: b2c2ca37670334b202ad31f1522ea42510b0da81681871871e283f02e42910ce 0.689656940000 1346148 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": 890139, "vin": [ { "gen": { "height": 890129 } } ], "vout": [ { "amount": 689656940, "target": { "key": "b2c2ca37670334b202ad31f1522ea42510b0da81681871871e283f02e42910ce" } } ], "extra": [ 1, 114, 19, 223, 131, 216, 21, 145, 79, 83, 24, 241, 218, 31, 36, 110, 133, 123, 220, 198, 65, 198, 28, 82, 176, 181, 64, 122, 47, 186, 78, 33, 215, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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