Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5572ce532205175236f217cce4ef939f513748526d73b7d33dcb96bfdb21456

Tx prefix hash: 3fea58ae351fd4fcfb24ffcfbce5bcf8d945dc6491befc5cca1f976a7aa64b04
Tx public key: 4ecc19072c0f010064bc80360e7a76f6f6f822ab776fe4da7b721a3d2d1a360a
Timestamp: 1728703730 Timestamp [UCT]: 2024-10-12 03:28:50 Age [y:d:h:m:s]: 00:246:04:51:16
Block: 1129726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175688 RingCT/type: yes/0
Extra: 014ecc19072c0f010064bc80360e7a76f6f6f822ab776fe4da7b721a3d2d1a360a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1e751fcf1487052b3887ba92a18023dac1726d3a2f67765401607f4f864b634 0.600000000000 1612575 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": 1129736, "vin": [ { "gen": { "height": 1129726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1e751fcf1487052b3887ba92a18023dac1726d3a2f67765401607f4f864b634" } } ], "extra": [ 1, 78, 204, 25, 7, 44, 15, 1, 0, 100, 188, 128, 54, 14, 122, 118, 246, 246, 248, 34, 171, 119, 111, 228, 218, 123, 114, 26, 61, 45, 26, 54, 10, 2, 17, 0, 0, 0, 3, 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