Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f249f26de25a777dab0a961bebec4af7d8ffd25fcb521e3f1df442f9f8c3374e

Tx prefix hash: 15bda65b486d688cd19f8c3e901616aad5994fc90da27f388a4b6645f183e6ba
Tx public key: f4785be9b2d510bca28f71f189f9f9ed07c9baec61413e950194b70a3993fd78
Timestamp: 1727391604 Timestamp [UCT]: 2024-09-26 23:00:04 Age [y:d:h:m:s]: 00:058:11:52:13
Block: 1118833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41804 RingCT/type: yes/0
Extra: 01f4785be9b2d510bca28f71f189f9f9ed07c9baec61413e950194b70a3993fd7802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f4de253c5e695ef52b31d59219e33e2ecd2e00a0e5987e71874751484408f7e 0.600000000000 1600166 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": 1118843, "vin": [ { "gen": { "height": 1118833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4de253c5e695ef52b31d59219e33e2ecd2e00a0e5987e71874751484408f7e" } } ], "extra": [ 1, 244, 120, 91, 233, 178, 213, 16, 188, 162, 143, 113, 241, 137, 249, 249, 237, 7, 201, 186, 236, 97, 65, 62, 149, 1, 148, 183, 10, 57, 147, 253, 120, 2, 17, 0, 0, 0, 3, 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