Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b654f2a043c6b4f8fceedf6e7b566473f7d23743d3998cf15ac6fcd632e2c4aa

Tx prefix hash: b8bde3dfd89487d3fa71ce8eb6885e2e822589b75f6b52ad1839d1390518cdfc
Tx public key: 0aec3b783e4afa4e304355183cfdd1e42787dfc4688800c34e6c62e0023e690f
Timestamp: 1645828222 Timestamp [UCT]: 2022-02-25 22:30:22 Age [y:d:h:m:s]: 02:346:13:10:39
Block: 446490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766838 RingCT/type: yes/0
Extra: 010aec3b783e4afa4e304355183cfdd1e42787dfc4688800c34e6c62e0023e690f02110000000306faf294000000000000000000

1 output(s) for total of 20.351366111000 dcy

stealth address amount amount idx
00: 30021f5ab9940ee6d26939564e2ff16b65bf4edf68abc76855bcc563e0c425fc 20.351366111000 860393 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": 446500, "vin": [ { "gen": { "height": 446490 } } ], "vout": [ { "amount": 20351366111, "target": { "key": "30021f5ab9940ee6d26939564e2ff16b65bf4edf68abc76855bcc563e0c425fc" } } ], "extra": [ 1, 10, 236, 59, 120, 62, 74, 250, 78, 48, 67, 85, 24, 60, 253, 209, 228, 39, 135, 223, 196, 104, 136, 0, 195, 78, 108, 98, 224, 2, 62, 105, 15, 2, 17, 0, 0, 0, 3, 6, 250, 242, 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