Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6fa638cb7de935afb61bdef4e04a08bc19cba4fa302688d7a0506da3ac1ce5

Tx prefix hash: 955fc0fa896b82b8ccbfb04e337675063a7f3da4faf63e6b6731f0836a5c42e9
Tx public key: 7af0ab8e19e9adfc70f782b8afb39d0f6bf0a661c9024881a9834b8dbc7683fc
Timestamp: 1716133053 Timestamp [UCT]: 2024-05-19 15:37:33 Age [y:d:h:m:s]: 00:328:13:58:02
Block: 1025499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234856 RingCT/type: yes/0
Extra: 017af0ab8e19e9adfc70f782b8afb39d0f6bf0a661c9024881a9834b8dbc7683fc02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa2befe8c3e412a5dd2c602d107f3d8fb2fa107fe5f6c90a29e5d49b7ef4c56 0.600000000000 1492054 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": 1025509, "vin": [ { "gen": { "height": 1025499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa2befe8c3e412a5dd2c602d107f3d8fb2fa107fe5f6c90a29e5d49b7ef4c56" } } ], "extra": [ 1, 122, 240, 171, 142, 25, 233, 173, 252, 112, 247, 130, 184, 175, 179, 157, 15, 107, 240, 166, 97, 201, 2, 72, 129, 169, 131, 75, 141, 188, 118, 131, 252, 2, 17, 0, 0, 0, 3, 82, 212, 126, 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