Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 409872bf8992ecfd80779e30a6a670ff28ae55ca7ba11e78b85fb5e2290fb6f4

Tx prefix hash: fa2f539a1cc3f6649e5365807c0ad909c5c84d3a03a2171d4e965e831a9a993c
Tx public key: 0b58c1ff0719f3647e76c0f1b2424daae3dc07f2442e8a8f486eb1de9106e63b
Timestamp: 1724665060 Timestamp [UCT]: 2024-08-26 09:37:40 Age [y:d:h:m:s]: 00:287:15:06:19
Block: 1096222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205481 RingCT/type: yes/0
Extra: 010b58c1ff0719f3647e76c0f1b2424daae3dc07f2442e8a8f486eb1de9106e63b02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c50fcacb4a2defb3d531ed5b8c4ed173446ad6b81cd782a1cf9fa76d7002441 0.600000000000 1571409 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": 1096232, "vin": [ { "gen": { "height": 1096222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c50fcacb4a2defb3d531ed5b8c4ed173446ad6b81cd782a1cf9fa76d7002441" } } ], "extra": [ 1, 11, 88, 193, 255, 7, 25, 243, 100, 126, 118, 192, 241, 178, 66, 77, 170, 227, 220, 7, 242, 68, 46, 138, 143, 72, 110, 177, 222, 145, 6, 230, 59, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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