Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 750628c304f41fefd89463053b8dea5834c8bdfb7a9c1757242147fce338bcde

Tx prefix hash: 4302189c95cff0d9fb7407c1044d26462418e1e7e4fd2a7ac44a15d052f72863
Tx public key: 6f9465e0083da1771d102273c2b93f5ea4aaf0fc9fd0326efbbd355cde270ee0
Timestamp: 1727642352 Timestamp [UCT]: 2024-09-29 20:39:12 Age [y:d:h:m:s]: 00:170:23:14:34
Block: 1120921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122003 RingCT/type: yes/0
Extra: 016f9465e0083da1771d102273c2b93f5ea4aaf0fc9fd0326efbbd355cde270ee002110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a65cdcb4d3c540b4810a5fb93db77c62d7bf6a58730e28f04dd0cfaed93d4cce 0.600000000000 1603008 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": 1120931, "vin": [ { "gen": { "height": 1120921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a65cdcb4d3c540b4810a5fb93db77c62d7bf6a58730e28f04dd0cfaed93d4cce" } } ], "extra": [ 1, 111, 148, 101, 224, 8, 61, 161, 119, 29, 16, 34, 115, 194, 185, 63, 94, 164, 170, 240, 252, 159, 208, 50, 110, 251, 189, 53, 92, 222, 39, 14, 224, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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